fix: use CPU-aware prover scheduler - #897
Open
jotabulacios wants to merge 3 commits into
Open
Conversation
Collaborator
Author
|
/bench |
Benchmark — real block (
|
| Metric | main | PR | Δ |
|---|---|---|---|
| Peak heap | 47024 MB | 51649 MB | +4625 MB (+9.8%) 🔴 |
| Prove time | 157.521s | 137.807s | -19.714s (-12.5%) 🟢 |
🎉 Improvement on the real block — prove time down 12.5%.
Prove-time spread 0.6% (138.162s / 137.807s / 137.367s)
Commit: 7b95345 · Baseline: cached · Runner: self-hosted bench
jotabulacios
marked this pull request as ready for review
August 4, 2026 20:33
Collaborator
|
/bench |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes the CPU proving regression introduced by the table scheduler.
The GPU scheduler uses external driver threads to admit and overlap table work. On CPU, that caused table tasks to launch nested Rayon work from outside the Rayon pool, leading to oversubscription, cache contention, and memory-bandwidth contention.
The CPU path now:
The CUDA path and proof format are unchanged.